Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@apps/expo-app/app/`(app)/auth/sign-up.tsx:
- Line 33: Update the CTA string in the Text element inside the sign-up
component so it matches the surrounding sentence-case copy style; replace
"Already have an Account? Sign In." with "Already have an account? Sign in." in
the JSX Text node (the line rendering the CTA in
apps/expo-app/app/(app)/auth/sign-up.tsx).

In `@apps/expo-app/components/settings/theme-mode-toggle.tsx`:
- Around line 20-24: The onValueChange handler for the theme toggle currently
awaits AsyncStorage.setItem without catching rejections; wrap the await call in
a try/catch inside the onValueChange async function (the handler that calls
setColorScheme and AsyncStorage.setItem) to handle storage failures, log a
non-sensitive error via your logger or console.error, and consider reverting or
ensuring UI/state consistency if setting storage fails (e.g., keep
setColorScheme but surface the error); do not swallow the error silently and
include identifiable context like the theme value and that the failure occurred
in AsyncStorage.setItem.

In `@packages/features/account/src/lib/hooks/use-update-avatar.ts`:
- Around line 38-40: The current flow deletes the previous avatar via
deleteAvatarObject before the new upload/update is committed, and
storage.remove() errors are silently ignored; change the flow in
use-update-avatar (the hook) to first upload the new avatar and commit the
user/profile update referencing the new URL, then only after a successful commit
call deleteAvatarObject for the old URL so the user never loses the current
avatar if upload/update fails, and modify deleteAvatarObject (and any direct
storage.remove() call) to catch and handle errors (log and surface/return them
instead of swallowing) so storage.remove failures are handled comprehensively.
- Line 100: The remove(...) call is currently ignoring storage errors; change it
to follow the same pattern as uploadAvatarBytes by awaiting
client.storage.from(AVATARS_BUCKET).remove([fileName]) and destructuring the
result into { data, error } (or similar), then throw or propagate the error if
present so deletions aren't silently swallowed; update the remove call inside
useUpdateAvatar (referencing AVATARS_BUCKET and the client.storage.remove
invocation) to handle and surface any storage errors.

In `@packages/ui/src/components/ui/accordion.tsx`:
- Around line 1-14: The file uses React types via React.ComponentProps (seen in
the props for components such as the AccordionTrigger, AccordionItem,
AccordionContent, and others where React.ComponentProps is referenced) but never
imports React; add an import for React (e.g., import * as React from 'react' or
import React from 'react') at the top of the file so the type references
resolve, keeping the existing imports intact and without changing runtime
behavior.

In `@packages/ui/src/components/ui/alert.tsx`:
- Around line 1-11: The type aliases AlertTitleProps, AlertDescriptionProps,
AlertIconProps and AlertActionsProps use React.ComponentProps but React isn't
imported as a namespace; modify the top import from 'react' to also import the
type ComponentProps (e.g., add "type ComponentProps" to the import list) and
change those aliases to use ComponentProps<...> instead of
React.ComponentProps<...> so the types resolve correctly.

In `@packages/ui/src/components/ui/badge.tsx`:
- Line 43: The destructive badge variant uses a fixed Tailwind class
'text-white' which breaks theme semantics; in the badge variant map (look for
the object or constant assigning destructive: 'text-white' inside the Badge
component or its variants in badge.tsx) replace that fixed class with the
semantic token 'text-destructive-foreground' (or the project’s equivalent
semantic foreground token) so the destructive badge uses theme-aware foreground
styling instead of a hardcoded white.

In `@packages/ui/src/components/ui/native-only-animated-view.tsx`:
- Around line 16-19: The web branch currently returns a Fragment and drops
wrapper props; change the Platform.OS === 'web' branch to render a View that
spreads the incoming props and wraps children so className, style, pointerEvents
and event handlers are preserved (i.e., replace the Fragment with a View
{...props}>{props.children}</View>), and ensure View is imported if not already;
locate the web branch check around Platform.OS === 'web' in
native-only-animated-view.tsx and compare it with the else branch that returns
Animated.View to keep prop parity.

In `@packages/ui/src/components/ui/progress.tsx`:
- Around line 12-24: The Progress component destructures value but never passes
it to ProgressPrimitive.Root, which breaks accessibility; update the Progress
function so ProgressPrimitive.Root receives the value prop (i.e., include value
in the props passed to ProgressPrimitive.Root) while keeping Indicator receiving
value as before; locate the Progress component and modify the JSX for
ProgressPrimitive.Root to forward the value prop (retain existing
className/props and indicatorClassName handling for Indicator).

In `@packages/ui/src/components/ui/switch.tsx`:
- Around line 16-29: The styling uses props.checked which only works for
controlled mode; update the conditional class logic on SwitchPrimitives.Thumb
(and the outer Switch container if present) to rely on the primitive's
data-state attribute selectors instead of props.checked—remove branches that
check props.checked and replace with data-state="checked"/data-state="unchecked"
based class toggles so the visual translate-x and dark:bg classes reflect the
actual DOM state for both controlled and uncontrolled (defaultChecked) usage.

In `@packages/ui/src/components/ui/tabs.tsx`:
- Around line 1-4: The file uses the type helper React.ComponentProps in several
places (e.g., in the TabsPrimitive-related prop types and exported components)
but never imports React for type references; add an explicit import for React at
the top of the file (e.g., import * as React from 'react') so all
React.ComponentProps type usages (in the
TabsRoot/TabsList/TabsTrigger/TabsContent prop types and any other locations)
resolve correctly without changing runtime behavior.

In `@packages/ui/src/components/ui/text.tsx`:
- Around line 55-56: The block mapping in the text variant assigns invalid ARIA
roles by casting 'blockquote' and 'code' to Role; update the mapping in the Text
component (the object containing blockquote and code entries) to stop assigning
ARIA roles for these variants — remove the Platform.select(... as Role) casts
and either omit the role entries or set them to undefined so the semantic HTML
elements render without an explicit role; ensure no other code in the Text
component (or related render/variant handlers) relies on those role values.

In `@packages/ui/src/components/ui/toggle.tsx`:
- Around line 50-57: The TextClassContext value currently includes the full root
className via the cn(...) call which leaks layout/container classes; update the
value passed to TextClassContext in the toggle component so it only contains
text-related classes (e.g., the 'text-sm native:text-lg text-foreground
font-medium' base classes plus the pressed-dependent color from
props.pressed/Platform.select) and remove the root props.className from that
cn(...) invocation; keep props.className applied to the root element only and
ensure references to value={...}, cn(...), props.pressed, and
Platform.select(...) are adjusted accordingly.

In `@packages/ui/src/lib/validation-errors.ts`:
- Around line 7-11: The current top-level-only extraction (variables first and
firstMessage) misses nested FieldErrors; replace it with a small recursive
extractor (e.g., findFirstErrorMessage(errors)) that walks objects/arrays in the
supplied errors structure, returns the first encountered .message string
(coercing to String) and use that value instead of firstMessage; update the
places that reference first/firstMessage to call this helper so nested
FieldErrorsImpl entries are discovered.

In `@tooling/typescript-config/base.json`:
- Line 20: Remove the global "node" typing from the base compilerOptions.types
in tooling/typescript-config/base.json so the base no longer forces Node types
on all packages; update the "types" array (currently ["nativewind/types",
"node"]) to omit "node", and add a note or document that packages which require
Node typings (e.g., the supabase package that uses process.env) should
explicitly opt-in by adding "node" to their own compilerOptions.types in their
local tsconfig (packages/ui, packages/features/auth, packages/features/account,
packages/supabase as needed).

---

Outside diff comments:
In `@packages/features/auth/src/password-reset/password-reset-form.tsx`:
- Around line 43-50: The success toast is shown immediately after calling
passwordResetMutation.mutate instead of waiting for the request to complete;
update the form.handleSubmit handler so that mutate is called with an options
object containing an onSuccess callback that calls toast.success('We sent you an
email to reset your password.'), and keep validation errors routed through
onValidationErrors as before; reference the passwordResetMutation.mutate call in
the password-reset-form component (which uses useRequestResetPassword), and
optionally add an onError callback to the mutate options to show toast.error on
failure.

---

Nitpick comments:
In `@packages/ui/src/components/ui/alert-dialog.tsx`:
- Around line 37-41: The JSX wraps children in an unnecessary fragment inside
NativeOnlyAnimatedView; update the render in the alert dialog component to pass
children directly to NativeOnlyAnimatedView (remove the <> {children} </>
wrapper) while keeping the existing entering and exiting props
(FadeIn.duration(200).delay(50) and FadeOut.duration(150)) so only
NativeOnlyAnimatedView, entering, exiting and children remain.

In `@packages/ui/src/components/ui/button.tsx`:
- Around line 95-97: The ButtonProps union incorrectly includes
React.RefAttributes<typeof Pressable>, which uses the component constructor type
and is redundant because React.ComponentProps<typeof Pressable> already includes
the ref in React 19; remove the React.RefAttributes<typeof Pressable> part so
ButtonProps becomes React.ComponentProps<typeof Pressable> & VariantProps<typeof
buttonVariants>, or if an explicit ref type is required use
React.RefAttributes<React.ComponentRef<typeof Pressable>> instead.

In `@packages/ui/src/components/ui/card.tsx`:
- Around line 24-50: The CardTitle/CardDescription prop types use incorrect
React.RefAttributes<typeof Text> and ref handling is inconsistent: remove the
explicit RefAttributes usage and rely on React.ComponentProps<typeof Text>
(which already includes ref in React 18+/19), and make both components forward
refs consistently by converting them to React.forwardRef wrappers (forward the
ref into the underlying Text element in both CardTitle and CardDescription);
update function signatures to use React.forwardRef and ensure you forward the
ref to the Text component (preserve className merging with cn and other props)
so both components have correct types and consistent ref behavior.

In `@packages/ui/src/components/ui/context-menu.tsx`:
- Around line 100-108: The code incorrectly asserts overlayStyle as typeof
StyleSheet.absoluteFill; remove that inaccurate assertion and ensure
overlayStyle is typed as a ViewStyle (or RegisteredStyle<ViewStyle>) instead.
Update the ContextMenu/overlay block that uses Platform.select,
StyleSheet.flatten and StyleSheet.absoluteFill so the flattened array is typed
like [StyleSheet.absoluteFill, overlayStyle as ViewStyle] (or cast overlayStyle
where it is defined to ViewStyle) rather than overlayStyle as typeof
StyleSheet.absoluteFill; alternatively import ViewStyle from react-native and
declare overlayStyle: ViewStyle | undefined to satisfy the type system.

In `@packages/ui/src/components/ui/dialog.tsx`:
- Around line 40-44: Replace the nested NativeOnlyAnimatedView pair with a
single NativeOnlyAnimatedView that merges the timing (use FadeIn with the 50ms
delay and 200ms duration and a single FadeOut.duration(150) for exiting) and
render {children} directly; update the component that uses
NativeOnlyAnimatedView (and references to FadeIn/FadeOut) to remove the extra
wrapper and redundant fragment so the animation timings are combined in one
view.

In `@packages/ui/src/components/ui/dropdown-menu.tsx`:
- Around line 106-114: The type assertion overlayStyle as typeof
StyleSheet.absoluteFill is incorrect; remove that assertion and pass
overlayStyle directly to StyleSheet.flatten (which accepts
StyleProp<ViewStyle>), so modify the Platform.select branch used in the
component where overlayStyle is passed (the StyleSheet.flatten call alongside
StyleSheet.absoluteFill) to call StyleSheet.flatten([StyleSheet.absoluteFill,
overlayStyle]) without the cast, ensuring overlayStyle retains its declared
StyleProp<ViewStyle> type.

In `@packages/ui/src/components/ui/menubar.tsx`:
- Around line 55-62: The Menubar is giving internal state precedence over the
controlled prop; change the component to prioritize the consumer's prop by using
valueProp before internal value (i.e., pass value={valueProp ?? value} to
MenubarPrimitive.Root), keep the existing onValueChange handler pattern
(onValueChange={onValueChangeProp ?? setValue}), and ensure the internal state
initializer for value reads from valueProp when present (initialize value state
from valueProp as the default) so controlled mode consistently wins and initial
render is correct; reference MenubarPrimitive.Root, valueProp, value,
onValueChangeProp, setValue, and closeMenu when making the edits.

In `@packages/ui/src/components/ui/tooltip.tsx`:
- Around line 29-35: The entering animation only distinguishes side === 'top' vs
other, causing left/right tooltips to use FadeInUp; update the
NativeOnlyAnimatedView entering logic (the entering prop where side is checked)
to handle 'left' and 'right' explicitly (e.g., map 'left' -> FadeInLeft, 'right'
-> FadeInRight, 'bottom' -> FadeInUp, 'top' -> FadeInDown) so mobile matches the
web behavior; modify the conditional/branch that currently uses FadeInDown and
FadeInUp to a small switch or lookup that returns the correct FadeIn* animation
for each side.